Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hotfix haiku not support vision #5771

Conversation

lloydzhou
Copy link
Contributor

@lloydzhou lloydzhou commented Nov 5, 2024

💻 变更类型 | Change Type

  • feat
  • fix
  • refactor
  • perf
  • style
  • test
  • docs
  • ci
  • chore
  • build

🔀 变更说明 | Description of Change

📝 补充信息 | Additional Information

Summary by CodeRabbit

  • New Features

    • Updated logic for identifying vision models, enhancing model classification with new keywords.
  • Bug Fixes

    • Removed outdated keyword to improve accuracy in model identification.

Copy link

vercel bot commented Nov 5, 2024

@lloydzhou is attempting to deploy a commit to the NextChat Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Nov 5, 2024

Walkthrough

The changes involve modifications to the isVisionModel function in the app/utils.ts file. The function's logic for identifying vision models has been updated by removing the keyword "claude-3" and adding two new keywords, "-sonnet-" and "-opus-". This adjustment affects how the function matches model identifiers to determine if they correspond to vision models. No other functions or exported entities were altered.

Changes

File Change Summary
app/utils.ts Modified isVisionModel function: removed "claude-3", added "-sonnet-" and "-opus-" to keywords.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Utils
    User->>Utils: Check if model is vision model
    Utils->>Utils: Evaluate model string
    Utils->>Utils: Match against keywords
    alt Match found
        Utils-->>User: Return true
    else No match
        Utils-->>User: Return false
    end
Loading

🐇 In the meadow, the models play,
With keywords new, they find their way.
No more "claude-3" in the mix,
"-sonnet-" and "-opus-" do the tricks!
Hopping along, we celebrate,
Changes made, oh, how great! 🌼


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@lloydzhou lloydzhou requested a review from Dogtiti November 5, 2024 11:18
Copy link
Contributor

github-actions bot commented Nov 5, 2024

Your build has completed!

Preview deployment

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
app/utils.ts (1)

259-260: Consider adding a comment explaining the model mappings.

To improve maintainability, consider adding a comment that maps these keywords to their corresponding model variants (e.g., "-sonnet-" → Claude-3-Sonnet, "-opus-" → Claude-3-Opus).

  const visionKeywords = [
    "vision",
+   // Claude-3 model variants
    "-sonnet-", // Claude-3-Sonnet
    "-opus-",   // Claude-3-Opus
    "gemini-1.5-pro",
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 00d6cb2 and 54d6bea.

📒 Files selected for processing (1)
  • app/utils.ts (1 hunks)
🔇 Additional comments (1)
app/utils.ts (1)

259-260: LGTM! Please verify Claude-3 model identifiers.

The addition of "-sonnet-" and "-opus-" keywords provides more precise identification of Claude-3 vision-capable models. This change aligns with the PR's objective to fix vision support.

Let's verify the model identifiers in the codebase:

✅ Verification successful

Vision support correctly configured for Claude-3 model variants

The verification confirms that the added keywords "-sonnet-" and "-opus-" correctly match the Claude-3 model identifiers found in app/constant.ts:

  • claude-3-sonnet-20240229
  • claude-3-opus-20240229
  • claude-3-opus-latest
  • claude-3-5-sonnet-20240620
  • claude-3-5-sonnet-20241022
  • claude-3-5-sonnet-latest

The changes ensure proper vision capability detection for both Claude-3 and Claude-3.5 variants.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for Claude-3 model references to confirm the correct identifiers
rg -i "claude.*3|sonnet|opus" --type ts

Length of output: 6981

@lloydzhou
Copy link
Contributor Author

是接口问题,不是模型支持的问题

@lloydzhou lloydzhou closed this Nov 5, 2024
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


It's an interface problem, not a model support problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants